1·The disadvantage with this scenario is that designer can delete elements or make changes that can break code previously written by the developer.
此案例的缺点在于，设计人员可能会删除项目或进行变更，而破坏了先前由开发人员所撰写的程序码。
2·But they couldn't break the code.
但是他们一直不能破译这些密码。
3·If you ignore the tests forever, the code they're expected to test may break and the breakage may not be detected.
如果永远忽略这些测试，那么它们期望测试的代码可能会中断，并且这样的中断可能不能被检测到。
4·If we were to take the strict position of "never break existing code," we would be forced to reject this useful new feature.
如果我们有严格地立场，“从不破坏现有代码”，那么我们将被迫拒绝这项有用的新功能。
5·Changing these values would change the hash code, which would in turn break any hash table or dictionary that the object happened to be stored in.
而改变那些值的同时也改变了哈希码，然后会破坏一些哈希表或者恰好储存了对象的字典。
6·If you break something, it's your responsibility to fix it, no matter where it is in the code.
如果您破坏了某些事物，您要负责进行修补，无论它位于代码的哪一部分。
7·When you modify old code you have to both test your changes and then perform a set of regression tests to make sure you didn't break any of the existing code.
而当你修改旧有代码时，你不得不既要测试你更改的部分，还要进行一系列的兼容测试，以保证你没有破坏任何的旧有代码。
8·In addition to promoting code reuse, it can also break complex transforms into chunks that are easy to understand.
除了促进代码重用，它还可以将复杂的转换分成易于理解的程序块。
9·Worse, even important modifications, such as upgrades to existing components, can cause things to break throughout the code base.
更糟糕的是，即使像对现有组件的升级这样的重要修改也会导致整个代码基中断的事情出现。
10·Because when you change the code, you break things and introduce many bugs.
因为当你改变代码时，有可能破坏了一些东西并造成许多漏洞。